Indeed we have seen a few reports of that but have never seen it here. If it happens again and anything is logged at that point or, even better, if you can find a way to replicate it please let us know. There have been similar issues in the past but not for quite a while.

The key line there is that the boot drive, ada0, detaches from the drive controller. That obviously stops it booting. That looks like a drive or controller failure. It could be something as simple as a bad SATA cable though.

First of all thank you for your reply @stephenw10 ! Ok - this was an odd one. We had a firewall alias for testing purposes to block updates to the ACB service. And yes - there way a typo ;-)

@stephenw10 [image: 1697051073163-3d8c8716-912f-47d5-b8da-df2548987dde-image.png]

It's this: https://redmine.pfsense.org/issues/14648 Try checking those sysctls directly. Steve

@stephenw10 Thanks got it!

If you are creating multiple rules for different ttl lengths remember to increment the sid: value for each rule.

A fresh install is always at the factory defaults anyway (unless you did a config recover during install?) so it would make no difference. Go ahead and restore your config and you should be good. The OK> prompt implies it wasn't able to get past the bootloader. And that is most commonly caused by something nuking the entire partition. Without more logs though it's hard to say what that might have been. Steve

@stephenw10 said in WOL Doesnt Seem To Be Working: Ethereal Your dating yourself with that name ;) hehehe

Ok, that would be expected because changing the NIC type means that the assigned vtnet2 interface no longer exists. I'm not sure why it asks for OPT1 and OPT4 unless those were assigned as the bridge/ovpns interfaces.

@Gertjan Thank you so much for taking the time to analyze my question and provide the screenshots. I appreciate. However, your scenario does not quite correspond to my use case. I'd rather devise a way to enter a device in a database and then automatically propagate its reserved IP, DNS name, etc.

error is related touname and not for meminfo. adding -- "--no-collector.uname" in extra flags has stopped errors. I ahve not seen any impact in data gathering as well as no grafana dashboards are not impacted.

@netboy Never mind I had an entry error in hosts.conf!!!

Not as far as I know. As before it might be possible to bring it back as a package if any developers have the available cycles. Steve

Well you might be able to force it by setting the interface MTU sufficiently small on the interface closest to the laptop. Or on the laptop itself. There are a lot of reports of it being broken in the Fortinet client though.

@Prez_Mgmt Ok can confirm releasing the ip, puling out the ethernet and adding it back sorted that.. thanks for all your help @viragomann

@Gertjan Thank you.

@PsyMan2000 said in disaster recovery: any 3rd party backups for CE or plus that will do a full job? Have a look at this. All you need is a 'Windows' PC. Even better would be a server type Microsoft device. All you need to do is creating a "Microsoft Windows Cron task" (scheduler something) and have it execute every day - mine fires at 08h00 AM (moments before I start to mess with my pfSense). It will do a SSH login, retrieve the current config, and manage your downloaded config files, so you can say "keep the latest 100 days". A real "set it and forget it tool" - and is a nice complement to the ABC solution. Btw : other, comparable solution exist, I guess.

@makq not sure whats exactly your question, but yes we have two VDSL and one LTE WAN.

It's a known issue with log rotation. Some of those firewall logs are rotating at ~1min intervals which I would class as quickly rotating. Though I can't actually find a bug for it right now.